-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[12_6_X] Fix PostDQMOffline*
sequences in cmsDriver.py
#40294
Conversation
A new Pull Request was created by @elusian for CMSSW_12_6_X. It involves the following packages:
@cmsbuild, @perrotta, @rappoccio, @fabiocos, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here
|
backport of #40293 |
type bug-fix |
urgent
|
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-d73b95/29575/summary.html Comparison SummarySummary:
|
+1 |
This pull request is fully signed and it will be integrated in one of the next CMSSW_12_6_X IBs (tests are also fine) and once validation in the development release cycle CMSSW_13_0_X is complete. This pull request will be automatically merged. |
PR description:
When adding a DQM sequence to the command line options (e.g.
DQM:@miniAODDQM
), cmsDriver.py is supposed to add the relativePostDQMOffline
sequence as selected in autoDQM.py.However, due to this commit in CMSSW_12_6_0_pre3, this does not happen anymore.
After the commit
sequenceList
andpostSequenceList
are the same object at the same address and fillingsequenceList
inhibits the fill ofpostSequenceList
(sinceexpandMapping
sees no "@" in the array). Since the sequences are the same, no dqmofflineOnPAT_step is produced in the output.This PR splits the assigment into two lines, which makes
sequenceList
andpostSequenceList
distinct again.PR validation:
Created a simple config file passing
DQM:@miniAODDQM
to cmsDriver.py, requestedPostDQMOffline*
sequences are back in theprocess.schedule
as they were in CMSSW_12_6_0_pre2If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Backport of #40293 for CMSSW 12_6_X